Low Jitter Event Synchronization Across Communication Links

ABSTRACT

Various embodiments use prospective synchronization signals early in the signal reception to adjust framing cycles of communication nodes to reduce jitter. Some embodiments temporarily suspend messaging between existing nodes of a communication system while instructing new nodes to generate a beacon according to a beacon schedule. The system can monitor for responses from the new node and calculate a timing error. This timing error can be sent to the new node to adjust cycle framing. In some embodiments, these techniques for timing the receive (Rx) and transmission (Tx) cycles of a node (e.g., a client wireless antenna system) can be utilized such that the radio frequency (RF) energy received between RF energy cycles can be delivered directly to the node, stored in a client&#39;s battery by a wireless charging system, enhance the Rx signal opportunities, or make the integrity of the delivered Tx signal more efficient.

BACKGROUND

Often there is a need to create tight time synchronization between two or more nodes in a network (e.g., networks with radios, fiber optics, IR, and/or other communication channels). Developing tight time synchronization with low jitter between these nodes can be critical and difficult to achieve. Examples where tight time synchronization with low jitter is needed includes, but is not limited to, entertainment devices such as video games consoles, display systems and controllers; industrial processes control equipment; and wireless power charging systems. Some systems, such as the link between video game controllers and consoles, require low latency. Other instances require very low jitter, i.e., a low deviation from a reference clock signal. For example, synchronizing the execution of the playing of video and audio in a wireless video game system where the audio playing device and video device are remote from the console often requires very low jitter. As video games systems typically run in a 30 or 60 Hz loop, the gaming systems need to keep these loops tightly synchronized to maintain coherence of the game play experience.

Current low power radio nodes have adopted multiple CPUs to ease software development requirements and increase total through put. For example, the Texas Instruments CC2650 or the Nordic nRF52 families of low power radios have multiple CPUs that are loosely coupled in the same chip. At the lowest level, closest to the RF components is a very simple sequencer, above the sequencer is typically a simple CPU that in the case of the CC2650 is an ARM M0 that handles the lowest level of the radio protocol. Above the ARM M0 often sits an ARM M3 that handles the higher level of the radio protocol and often a higher-level application program. In more complex systems, there is often an external dedicated application processor that handles the application program. All of these CPUs run asynchronously resulting in the potential for considerable jitter to stack-up. This stack-up occurs because events must pass up the processor stack before a message can be acted on. This can result in a loose temporal coupling when an application processor on one systems sends a message to another application processor on a different system.

Accordingly, a need exists for technology that overcomes the problem demonstrated above, as well as one that provides additional benefits. The examples provided herein of some prior or related systems and their associated limitations are intended to be illustrative and not exclusive. Other limitations of existing or prior systems will become apparent to those of skill in the art upon reading the following Detailed Description.

BRIEF DESCRIPTION OF THE DRAWINGS

One or more embodiments of the present invention are illustrated by way of example and not limitation in the figures of the accompanying drawings, in which like references indicate similar elements.

FIG. 1 depicts a block diagram including an example wireless power delivery environment illustrating wireless power delivery from one or more wireless power transmission systems to various wireless devices within the wireless power delivery environment in accordance with some embodiments.

FIG. 2 depicts a sequence diagram illustrating example operations between a wireless power transmission system and a wireless receiver client for commencing wireless power delivery in accordance with some embodiments.

FIG. 3 depicts a block diagram illustrating example components of a wireless power transmission system in accordance with some embodiments.

FIG. 4 depicts a block diagram illustrating example components of a wireless power receiver client in accordance with some embodiments.

FIGS. 5A and 5B depict diagrams illustrating an example multipath wireless power delivery environment in accordance with some embodiments.

FIG. 6 is block diagram illustrating a transaction processing system with auto restart in accordance with some embodiments.

FIG. 7 is a flowchart illustrating an example of a set of operations for adjusting cycle framing in accordance with some embodiments.

FIG. 8 depicts a sequence diagram illustrating communications between components to create an event synchronization in accordance with some embodiments.

FIG. 9 depicts a timing diagram illustrating example communications between components of a system in accordance with some embodiments.

FIG. 10 depicts a flow chart illustrating a set of operations for adding a new client in accordance with some embodiments.

FIG. 11 depicts a block diagram illustrating example components of a representative mobile device or tablet computer with a wireless power receiver or client in the form of a mobile (or smart) phone or tablet computer device in accordance with some embodiments.

FIG. 12 depicts a diagrammatic representation of a machine, in the example form, of a computer system within which a set of instructions, for causing the machine to perform any one or more of the methodologies discussed herein, may be executed.

DETAILED DESCRIPTION

The following description and drawings are illustrative and are not to be construed as limiting. Numerous specific details are described to provide a thorough understanding of the disclosure. However, in certain instances, well-known or conventional details are not described in order to avoid obscuring the description. References to one or an embodiment in the present disclosure can be, but not necessarily are, references to the same embodiment; and, such references mean at least one of the embodiments.

Reference in this specification to “one embodiment” or “an embodiment” means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment of the disclosure. The appearances of the phrase “in one embodiment” in various places in the specification are not necessarily all referring to the same embodiment, nor are separate or alternative embodiments mutually exclusive of other embodiments. Moreover, various features are described which may be exhibited by some embodiments and not by others. Similarly, various requirements are described which may be requirements for some embodiments but no other embodiments.

The terms used in this specification generally have their ordinary meanings in the art, within the context of the disclosure, and in the specific context where each term is used. Certain terms that are used to describe the disclosure are discussed below, or elsewhere in the specification, to provide additional guidance to the practitioner regarding the description of the disclosure. For convenience, certain terms may be highlighted, for example using italics and/or quotation marks. The use of highlighting has no influence on the scope and meaning of a term; the scope and meaning of a term is the same, in the same context, whether or not it is highlighted. It will be appreciated that same thing can be said in more than one way.

Consequently, alternative language and synonyms may be used for any one or more of the terms discussed herein, nor is any special significance to be placed upon whether or not a term is elaborated or discussed herein. Synonyms for certain terms are provided. A recital of one or more synonyms does not exclude the use of other synonyms. The use of examples anywhere in this specification, including examples of any terms discussed herein, is illustrative only, and is not intended to further limit the scope and meaning of the disclosure or of any exemplified term. Likewise, the disclosure is not limited to various embodiments given in this specification.

Without intent to further limit the scope of the disclosure, examples of instruments, apparatus, methods and their related results according to the embodiments of the present disclosure are given below. Note that titles or subtitles may be used in the examples for convenience of a reader, which in no way should limit the scope of the disclosure. Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure pertains. In the case of conflict, the present document, including definitions, will control.

Various embodiments of the present disclosure describe techniques for providing low jitter event synchronization across communication links. As a result, some embodiments provide synchronization between two or more nodes that have a loose communication link with little or no additional cost. In addition, some embodiments use the separation of data transmission timing from the decoding of the content of message to enable this capability. Various embodiments of these techniques can be used in ‘active beaconing’ wireless power delivery environments, stationary devices in home or industrial applications, Internet of Things (IoT) devices, and other devices where communication (e.g., radio-based communications, Ethernet-based communications, fiber optic communications, etc.) with low jitter is needed across the communication links.

Any headings provided herein are for convenience only and do not necessarily affect the scope or meaning of the claimed invention.

I. Wireless Power Transmission System Overview/Architecture

FIG. 1 depicts a block diagram including an example wireless power delivery environment 100 illustrating wireless power delivery from one or more wireless power transmission systems (WPTS) 101 a-n (also referred to as “wireless power delivery systems”, “antenna array systems” and “wireless chargers”) to various wireless devices 102 a-n within the wireless power delivery environment 100, according to some embodiments. More specifically, FIG. 1 illustrates an example wireless power delivery environment 100 in which wireless power and/or data can be delivered to available wireless devices 102 a-102 n having one or more wireless power receiver clients 103 a-103 n (also referred to herein as “clients” and “wireless power receivers”). The wireless power receiver clients are configured to receive and process wireless power from one or more wireless power transmission systems 101 a-101 n. Components of an example wireless power receiver client 103 are shown and discussed in greater detail with reference to FIG. 4.

As shown in the example of FIG. 1, the wireless devices 102 a-102 n include mobile phone devices and a wireless game controller. However, the wireless devices 102 a-102 n can be any device or system that needs power and is capable of receiving wireless power via one or more integrated wireless power receiver clients 103 a-103 n. As discussed herein, the one or more integrated wireless power receiver clients receive and process power from one or more wireless power transmission systems 101 a-101 n and provide the power to the wireless devices 102 a-102 n (or internal batteries of the wireless devices) for operation thereof.

Each wireless power transmission system 101 can include multiple antennas 104 a-n, e.g., an antenna array including hundreds or thousands of antennas, which are capable of delivering wireless power to wireless devices 102. In some embodiments, the antennas are adaptively-phased radio frequency (RF) antennas. The wireless power transmission system 101 is capable of determining the appropriate phases with which to deliver a coherent power transmission signal to the wireless power receiver clients 103. The array is configured to emit a signal (e.g., continuous wave or pulsed power transmission signal) from multiple antennas at a specific phase relative to each other. It is appreciated that use of the term “array” does not necessarily limit the antenna array to any specific array structure. That is, the antenna array does not need to be structured in a specific “array” form or geometry. Furthermore, as used herein the term “array” or “array system” may include related and peripheral circuitry for signal generation, reception and transmission, such as radios, digital logic and modems. In some embodiments, the wireless power transmission system 101 can have an embedded Wi-Fi hub for data communications via one or more antennas or transceivers.

The wireless devices 102 can include one or more wireless power receiver clients 103. As illustrated in the example of FIG. 1, power delivery antennas 104 a-104 n are shown. The power delivery antennas 104 a are configured to provide delivery of wireless radio frequency power in the wireless power delivery environment. In some embodiments, one or more of the power delivery antennas 104 a-104 n can alternatively or additionally be configured for data communications in addition to or in lieu of wireless power delivery. The one or more data communication antennas are configured to send data communications to and receive data communications from the wireless power receiver clients 103 a-103 n and/or the wireless devices 102 a-102 n. In some embodiments, the data communication antennas can communicate via Bluetooth™, Wi-Fi™, ZigBee™, etc. Other data communication protocols are also possible.

Each wireless power receiver client 103 a-103 n includes one or more antennas (not shown) for receiving signals from the wireless power transmission systems 101 a-101 n. Likewise, each wireless power transmission system 101 a-101 n includes an antenna array having one or more antennas and/or sets of antennas capable of emitting continuous wave or discrete (pulse) signals at specific phases relative to each other. As discussed above, each the wireless power transmission systems 101 a-101 n is capable of determining the appropriate phases for delivering the coherent signals to the wireless power receiver clients 102 a-102 n. For example, in some embodiments, coherent signals can be determined by computing the complex conjugate of a received beacon (or calibration) signal at each antenna of the array such that the coherent signal is phased for delivering power to the particular wireless power receiver client that transmitted the beacon (or calibration) signal.

Although not illustrated, each component of the environment, e.g., wireless device, wireless power transmission system, etc., can include control and synchronization mechanisms, e.g., a data communication synchronization module. The wireless power transmission systems 101 a-101 n can be connected to a power source such as, for example, a power outlet or source connecting the wireless power transmission systems to a standard or primary alternating current (AC) power supply in a building. Alternatively, or additionally, one or more of the wireless power transmission systems 101 a-101 n can be powered by a battery or via other mechanisms, e.g., solar cells, etc.

The wireless power receiver clients 102 a-102 n and/or the wireless power transmission systems 101 a-101 n are configured to operate in a multipath wireless power delivery environment. That is, the wireless power receiver clients 102 a-102 n and the wireless power transmission systems 101 a-101 n are configured to utilize reflective objects 106 such as, for example, walls or other RF reflective obstructions within range to transmit beacon (or calibration) signals and/or receive wireless power and/or data within the wireless power delivery environment. The reflective objects 106 can be utilized for multi-directional signal communication regardless of whether a blocking object is in the line of sight between the wireless power transmission system and the wireless power receiver clients 103 a-103 n.

As described herein, each wireless device 102 a-102 n can be any system and/or device, and/or any combination of devices/systems that can establish a connection with another device, a server and/or other systems within the example environment 100. In some embodiments, the wireless devices 102 a-102 n include displays or other output functionalities to present data to a user and/or input functionalities to receive data from the user. By way of example, a wireless device 102 can be, but is not limited to, a video game controller, a server desktop, a desktop computer, a computer cluster, a mobile computing device such as a notebook, a laptop computer, a handheld computer, a mobile phone, a smart phone, a PDA, a Blackberry device, a Treo, and/or an iPhone, etc. By way of example and not limitation, the wireless device 102 can also be any wearable device such as watches, necklaces, rings or even devices embedded on or within the customer. Other examples of a wireless device 102 include, but are not limited to, safety sensors (e.g., fire or carbon monoxide), electric toothbrushes, electronic door lock/handles, electric light switch controller, electric shavers, etc.

Although not illustrated in the example of FIG. 1, the wireless power transmission system 101 and the wireless power receiver clients 103 a-103 n can each include a data communication module for communication via a data channel. Alternatively, or additionally, the wireless power receiver clients 103 a-103 n can direct the wireless devices 102 a-102 n to communicate with the wireless power transmission system via existing data communications modules. In some embodiments, the beacon signal, which is primarily referred to herein as a continuous waveform, can alternatively or additionally take the form of a modulated signal.

FIG. 2 depicts a sequence diagram 200 illustrating example operations between a wireless power delivery system (e.g., WPTS 101) and a wireless power receiver client (e.g., wireless power receiver client 103) for establishing wireless power delivery in a multipath wireless power delivery, according to an embodiment. Initially, communication is established between the wireless power transmission system 101 and the power receiver client 103. The initial communication can be, for example, a data communication link that is established via one or more antennas 104 of the wireless power transmission system 101. As discussed, in some embodiments, one or more of the antennas 104 a-104 n can be data antennas, wireless power transmission antennas, or dual-purpose data/power antennas. Various information can be exchanged between the wireless power transmission system 101 and the wireless power receiver client 103 over this data communication channel. For example, wireless power signaling can be time sliced among various clients in a wireless power delivery environment. In such cases, the wireless power transmission system 101 can send beacon schedule information, e.g., Beacon Beat Schedule (BBS) cycle, power cycle information, etc., so that the wireless power receiver client 103 knows when to transmit (broadcast) its beacon signals and when to listen for power, etc.

Continuing with the example of FIG. 2, the wireless power transmission system 101 selects one or more wireless power receiver clients for receiving power and sends the beacon schedule information to the select wireless power receiver clients 103. The wireless power transmission system 101 can also send power transmission scheduling information so that the wireless power receiver client 103 knows when to expect (e.g., a window of time) wireless power from the wireless power transmission system. The wireless power receiver client 103 then generates a beacon (or calibration) signal and broadcasts the beacon during an assigned beacon transmission window (or time slice) indicated by the beacon schedule information, e.g., Beacon Beat Schedule (BBS) cycle. As discussed herein, the wireless power receiver client 103 includes one or more antennas (or transceivers) which have a radiation and reception pattern in three-dimensional space proximate to the wireless device 102 in which the wireless power receiver client 103 is embedded.

The wireless power transmission system 101 receives the beacon from the power receiver client 103 and detects and/or otherwise measures the phase (or direction) from which the beacon signal is received at multiple antennas. The wireless power transmission system 101 then delivers wireless power to the power receiver client 103 from the multiple antennas 103 based on the detected or measured phase (or direction) of the received beacon at each of the corresponding antennas. In some embodiments, the wireless power transmission system 101 determines the complex conjugate of the measured phase of the beacon and uses the complex conjugate to determine a transmit phase that configures the antennas for delivering and/or otherwise directing wireless power to the wireless power receiver client 103 via the same path over which the beacon signal was received from the wireless power receiver client 103.

In some embodiments, the wireless power transmission system 101 includes many antennas. One or more of the many antennas may be used to deliver power to the power receiver client 103. The wireless power transmission system 101 can detect and/or otherwise determine or measure phases at which the beacon signals are received at each antenna. The large number of antennas may result in different phases of the beacon signal being received at each antenna of the wireless power transmission system 101. As discussed above, the wireless power transmission system 101 can determine the complex conjugate of the beacon signals received at each antenna. Using the complex conjugates, one or more antennas may emit a signal that takes into account the effects of the large number of antennas in the wireless power transmission system 101. In other words, the wireless power transmission system 101 can emit a wireless power transmission signal from the one or more antennas in such a way as to create an aggregate signal from the one or more of the antennas that approximately recreates the waveform of the beacon in the opposite direction. Said another way, the wireless power transmission system 101 can deliver wireless RF power to the wireless power receiver clients via the same paths over which the beacon signal is received at the wireless power transmission system 101. These paths can utilize reflective objects 106 within the environment. Additionally, the wireless power transmission signals can be simultaneously transmitted from the wireless power transmission system 101 such that the wireless power transmission signals collectively match the antenna radiation and reception pattern of the client device in a three-dimensional (3D) space proximate to the client device.

As shown, the beacon (or calibration) signals can be periodically transmitted by wireless power receiver clients 103 within the power delivery environment according to, for example, the BBS, so that the wireless power transmission system 101 can maintain knowledge and/or otherwise track the location of the power receiver clients 103 in the wireless power delivery environment. The process of receiving beacon signals from a wireless power receiver client 103 at the wireless power transmission system and, in turn, responding with wireless power directed to that particular wireless power receiver client is referred to herein as retrodirective wireless power delivery.

Furthermore, as discussed herein, wireless power can be delivered in power cycles defined by power schedule information. A more detailed example of the signaling required to commence wireless power delivery is described now with reference to FIG. 3.

FIG. 3 depicts a block diagram illustrating example components of a wireless power transmission system 300, in accordance with an embodiment. As illustrated in the example of FIG. 3, the wireless charger 300 includes a master bus controller (MBC) board and multiple mezzanine boards that collectively comprise the antenna array. The MBC includes control logic 310, an external data interface (I/F) 315, an external power interface (I/F) 320, a communication block 330 and proxy 340. The mezzanine (or antenna array boards 350) each include multiple antennas 360 a-360 n. Some or all of the components can be omitted in some embodiments. Additional components are also possible. For example, in some embodiments only one of communication block 330 or proxy 340 may be included.

The control logic 310 is configured to provide control and intelligence to the array components. The control logic 310 may comprise one or more processors, FPGAs, memory units, etc., and direct and control the various data and power communications. The communication block 330 can direct data communications on a data carrier frequency, such as the base signal clock for clock synchronization. The data communications can be Bluetooth™, Wi-Fi™, ZigBee™, etc., including combinations or variations thereof. Likewise, the proxy 340 can communicate with clients via data communications as discussed herein. The data communications can be, by way of example and not limitation, Bluetooth™, Wi-Fi™, ZigBee™, etc. Other communication protocols are possible.

In some embodiments, the control logic 310 can also facilitate and/or otherwise enable data aggregation for Internet of Things (IoT) devices. In some embodiments, wireless power receiver clients can access, track and/or otherwise obtain IoT information about the device in which the wireless power receiver client is embedded and provide that IoT information to the wireless power transmission system 300 over a data connection. This IoT information can be provided to via an external data interface 315 to a central or cloud-based system (not shown) where the data can be aggregated, processed, etc. For example, the central system can process the data to identify various trends across geographies, wireless power transmission systems, environments, devices, etc. In some embodiments, the aggregated data and or the trend data can be used to improve operation of the devices via remote updates, etc. Alternatively, or additionally, in some embodiments, the aggregated data can be provided to third party data consumers. In this manner, the wireless power transmission system acts as a Gateway or Enabler for the IoTs. By way of example and not limitation, the IoT information can include capabilities of the device in which the wireless power receiver client is embedded, usage information of the device, power levels of the device, information obtained by the device or the wireless power receiver client itself, e.g., via sensors, etc.

The external power interface 320 is configured to receive external power and provide the power to various components. In some embodiments, the external power interface 320 may be configured to receive a standard external 24 Volt power supply. In other embodiments, the external power interface 320 can be, for example, 120/240 Volt AC mains to an embedded DC power supply which sources the required 12/24/48 Volt DC to provide the power to various components. Alternatively, the external power interface could be a DC supply which sources the required 12/24/48 Volts DC. Alternative configurations are also possible.

In operation, the master bus controller (MBC), which controls the wireless power transmission system 300, receives power from a power source and is activated. The MBC then activates the proxy antenna elements on the wireless power transmission system and the proxy antenna elements enter a default “discovery” mode to identify available wireless receiver clients within range of the wireless power transmission system. When a client is found, the antenna elements on the wireless power transmission system power on, enumerate, and (optionally) calibrate.

The MBC then generates beacon transmission scheduling information and power transmission scheduling information during a scheduling process. The scheduling process includes selection of power receiver clients. For example, the MBC can select power receiver clients for power transmission and generate a Beacon Beat Schedule (BBS) cycle and a Power Schedule (PS) for the selected wireless power receiver clients. As discussed herein, the power receiver clients can be selected based on their corresponding properties and/or requirements.

In some embodiments, the MBC can also identify and/or otherwise select available clients that will have their status queried in the Client Query Table (CQT). Clients that are placed in the CQT are those on “standby”, e.g., not receiving a charge. The BBS and PS are calculated based on vital information about the clients such as, for example, battery status, current activity/usage, how much longer the client has until it runs out of power, priority in terms of usage, etc.

The Proxy Antenna Element (AE) broadcasts the BBS to all clients. As discussed herein, the BBS indicates when each client should send a beacon. Likewise, the PS indicates when and to which clients the array should send power to and when clients should listen for wireless power. Each client starts broadcasting its beacon and receiving power from the array per the BBS and PS. The Proxy AE can concurrently query the Client Query Table to check the status of other available clients. In some embodiments, a client can only exist in the BBS or the CQT (e.g., waitlist), but not in both. The information collected in the previous step continuously and/or periodically updates the BBS cycle and/or the PS.

FIG. 4 is a block diagram illustrating example components of a wireless power receiver client 400, in accordance with some embodiments. As illustrated in the example of FIG. 4, the receiver 400 includes control logic 410, battery 420, an IoT control module 425, communication block 430 and associated antenna 470, power meter 440, rectifier 450, a combiner 455, beacon signal generator 460, beacon coding unit 462 and an associated antenna 480, and switch 465 connecting the rectifier 450 or the beacon signal generator 460 to one or more associated antennas 490 a-n. Some or all of the components can be omitted in some embodiments. For example, in some embodiments, the wireless power receiver client 400 does not include its own antennas but instead utilizes and/or otherwise shares one or more antennas (e.g., Wi-Fi antenna) of the wireless device in which the wireless power receiver client is embedded. Moreover, in some embodiments, the wireless power receiver client may include a single antenna that provides data transmission functionality as well as power/data reception functionality. Additional components are also possible.

A combiner 455 receives and combines the received power transmission signals from the power transmitter in the event that the receiver 400 has more than one antenna. The combiner can be any combiner or divider circuit that is configured to achieve isolation between the output ports while maintaining a matched condition. For example, the combiner 455 can be a Wilkinson Power Divider circuit. The rectifier 450 receives the combined power transmission signal from the combiner 455, if present, which is fed through the power meter 440 to the battery 420 for charging. In other embodiments, each antenna's power path can have its own rectifier 450 and the DC power out of the rectifiers is combined prior to feeding the power meter 440. The power meter 440 can measure the received power signal strength and provides the control logic 410 with this measurement.

Battery 420 can include protection circuitry and/or monitoring functions. Additionally, the battery 420 can include one or more features, including, but not limited to, current limiting, temperature protection, over/under voltage alerts and protection, and coulomb monitoring.

The control logic 410 receives and processes the battery power level from the battery 420 itself. The control logic 410 may also transmit/receive via the communication block 430 a data signal on a data carrier frequency, such as the base signal clock for clock synchronization. The beacon signal generator 460 generates the beacon signal, or calibration signal, transmits the beacon signal using either the antenna 480 or 490 after the beacon signal is encoded.

It may be noted that, although the battery 420 is shown as charged by, and providing power to, the wireless power receiver client 400, the receiver may also receive its power directly from the rectifier 450. This may be in addition to the rectifier 450 providing charging current to the battery 420, or in lieu of providing charging. Also, it may be noted that the use of multiple antennas is one example of implementation and the structure may be reduced to one shared antenna.

In some embodiments, the control logic 410 and/or the IoT control module 425 can communicate with and/or otherwise derive IoT information from the device in which the wireless power receiver client 400 is embedded. Although not shown, in some embodiments, the wireless power receiver client 400 can have one or more data connections (wired or wireless) with the device in which the wireless power receiver client 400 is embedded over which IoT information can be obtained. Alternatively, or additionally, IoT information can be determined and/or inferred by the wireless power receiver client 400, e.g., via one or more sensors. As discussed above, the IoT information can include, but is not limited to, information about the capabilities of the device in which the wireless power receiver client 400 is embedded, usage information of the device in which the wireless power receiver client 400 is embedded, power levels of the battery or batteries, of the device in which the wireless power receiver client 400 is embedded, and/or information obtained or inferred by the device in which the wireless power receiver client is embedded or the wireless power receiver client itself, e.g., via sensors, etc.

In some embodiments, a client identifier (ID) module 415 stores a client ID that can uniquely identify the wireless power receiver client 400 in a wireless power delivery environment. For example, the ID can be transmitted to one or more wireless power transmission systems when communication is established. In some embodiments, wireless power receiver clients may also be able to receive and identify other wireless power receiver clients in a wireless power delivery environment based on the client ID.

An optional motion sensor 495 can detect motion and signal the control logic 410 to act accordingly. For example, a device receiving power may integrate motion detection mechanisms such as accelerometers or equivalent mechanisms to detect motion. Once the device detects that it is in motion, it may be assumed that it is being handled by a user, and would trigger a signal to the array to either to stop transmitting power, or to lower the power transmitted to the device. In some embodiments, when a device is used in a moving environment like a car, train or plane, the power might only be transmitted intermittently or at a reduced level unless the device is critically low on power.

FIGS. 5A and 5B depict diagrams illustrating an example multipath wireless power delivery environment 500, according to some embodiments. The multipath wireless power delivery environment 500 includes a user operating a wireless device 502 including one or more wireless power receiver clients 503. The wireless device 502 and the one or more wireless power receiver clients 503 can be wireless device 102 of FIG. 1 and wireless power receiver client 103 of FIG. 1 or wireless power receiver client 400 of FIG. 4, respectively, although alternative configurations are possible. Likewise, wireless power transmission system 501 can be wireless power transmission system 101 FIG. 1 or wireless power transmission system 300 of FIG. 3, although alternative configurations are possible. The multipath wireless power delivery environment 500 includes reflective objects 506 and various absorptive objects, e.g., users, or humans, furniture, etc.

Wireless device 502 includes one or more antennas (or transceivers) that have a radiation and reception pattern 510 in three-dimensional space proximate to the wireless device 102. The one or more antennas (or transceivers) can be wholly or partially included as part of the wireless device 102 and/or the wireless power receiver client (not shown). For example, in some embodiments one or more antennas, e.g., Wi-Fi, Bluetooth, etc. of the wireless device 502 can be utilized and/or otherwise shared for wireless power reception. As shown in the example of FIGS. 5A and 5B, the radiation and reception pattern 510 comprises a lobe pattern with a primary lobe and multiple side lobes. Other patterns are also possible.

The wireless device 502 transmits a beacon (or calibration) signal over multiple paths to the wireless power transmission system 501. As discussed herein, the wireless device 502 transmits the beacon in the direction of the radiation and reception pattern 510 such that the strength of the received beacon signal by the wireless power transmission system, e.g., received signal strength indication (RSSI), depends on the radiation and reception pattern 510. For example, beacon signals are not transmitted where there are nulls in the radiation and reception pattern 510 and beacon signals are the strongest at the peaks in the radiation and reception pattern 510, e.g., peak of the primary lobe. As shown in the example of FIG. 5A, the wireless device 502 transmits beacon signals over five paths P₁-P₅. Paths P₄ and P₅ are blocked by reflective and/or absorptive object 506. The wireless power transmission system 501 receives beacon signals of increasing strengths via paths P₁-P₃. The bolder lines indicate stronger signals. In some embodiments, the beacon signals are directionally transmitted in this manner, for example, to avoid unnecessary RF energy exposure to the user.

A fundamental property of antennas is that the receiving pattern (sensitivity as a function of direction) of an antenna when used for receiving is identical to the far-field radiation pattern of the antenna when used for transmitting. This is a consequence of the reciprocity theorem in electromagnetism. As shown in the example of FIGS. 5A and 5B, the radiation and reception pattern 510 is a three-dimensional lobe shape. However, the radiation and reception pattern 510 can be any number of shapes depending on the type or types, e.g., horn antennas, simple vertical antenna, etc. used in the antenna design. For example, the radiation and reception pattern 510 can comprise various directive patterns. Any number of different antenna radiation and reception patterns are possible for each of multiple client devices in a wireless power delivery environment.

Referring again to FIG. 5A, the wireless power transmission system 501 receives the beacon (or calibration) signal via multiple paths P₁-P₃ at multiple antennas or transceivers. As shown, paths P₂, and P₃ are direct line of sight paths while path P₁ is a non-line of sight path. Once the beacon (or calibration) signal is received by the wireless power transmission system 501, the power transmission system 501 processes the beacon (or calibration) signal to determine one or more receive characteristics of the beacon signal at each of the multiple antennas. For example, among other operations, the wireless power transmission system 501 can measure the phases at which the beacon signal is received at each of the multiple antennas or transceivers.

The wireless power transmission system 501 processes the one or more receive characteristics of the beacon signal at each of the multiple antennas to determine or measure one or more wireless power transmit characteristics for each of the multiple RF transceivers based on the one or more receive characteristics of the beacon (or calibration) signal as measured at the corresponding antenna or transceiver. By way of example and not limitation, the wireless power transmit characteristics can include phase settings for each antenna or transceiver, transmission power settings, etc.

As discussed herein, the wireless power transmission system 501 determines the wireless power transmit characteristics such that, once the antennas or transceivers are configured, the multiple antennas or transceivers are operable to transit a wireless power signal that matches the client radiation and reception pattern in the three-dimensional space proximate to the client device. FIG. 5B illustrates the wireless power transmission system 501 transmitting wireless power via paths P1-P3 to the wireless device 502. Advantageously, as discussed herein, the wireless power signal matches the client radiation and reception pattern 510 in the three-dimensional space proximate to the client device. Said another way, the wireless power transmission system will transmit the wireless power signals in the direction in which the wireless power receiver has maximum gain, e.g., will receive the most wireless power. As a result, no signals are sent in directions in which the wireless power receiver cannot receiver, e.g., nulls and blockages. In some embodiments, the wireless power transmission system 501 measures the RSSI of the received beacon signal and if the beacon is less than a threshold value, the wireless power transmission system will not send wireless power over that path.

The three paths shown in the example of FIGS. 5A and 5B are illustrated for simplicity, it is appreciated that any number of paths can be utilized for transmitting power to the wireless device 502 depending on, among other factors, reflective and absorptive objects in the wireless power delivery environment.

Although the example of FIG. 5A illustrates transmitting a beacon (or calibration) signal in the direction of the radiation and reception pattern 510, it is appreciated that, in some embodiments, beacon signals can alternatively or additionally be omnidirectionally transmitted.

II. Low Jitter Synchronization

Many communication applications require that low jitter synchronization occur between two or more nodes. Current synchronization implementations allow a message to travel up multiple software stacks that are running asynchronously through multiple CPUs that add jitter at each level before decoding a message and issuing a synchronization signal. In contrast, various embodiments use a prospective synchronization signal early in the signal reception. Then, once the message content is decoded, confirms that the prospective message is valid. For example, in some embodiments, these techniques for timing the receive (Rx) and transmission (Tx) cycles of a client (e.g., a client wireless antenna system) can be utilized such that the radio frequency (RF) energy received between RF energy cycles can be delivered directly to the device or stored in a client's battery by a wireless charging system, enhance the Rx signal opportunities, or make the integrity of the delivered Tx signal more efficient.

FIG. 6 is block diagram illustrating a tone power scheduling system with auto restart in accordance with some embodiments. In retrodirective wireless power delivery environments, wireless power receivers generate and send beacon signals that are received by an array of antennas of a wireless power transmission system. The beacon signals provide the charger with timing information for wireless power transfers, and also indicate directionality of the incoming signal. As discussed herein, this directionality information is employed when transmitting in order to focus energy (e.g., power wave delivery) on individual wireless power receiver clients.

A tone power schedule (TPS) system builds on top of the BBS system, adding another layer of configuration beyond the time settings that determine how long a client will tone and how long it will receive power. U.S. application Ser. No. 15/367,403 filed on Dec. 2, 2016 entitled “Tone Power Scheduler for Wireless Environmental Applications” describes some implementations of a TPS system. U.S. application Ser. No. 15/367,403 is hereby incorporated in its entirety for all purposes.

The TPS system can be both time- and client-aware. Using TPS, a power charging system can time-divide power delivery among several clients during a single Beacon Beat, enabling much more flexibility in the system for clients that may move frequently, have greater-than-average power needs, or have other special considerations. The TPS also creates a common language (i.e., the control register set) used between software, transmitter, and receiver clients, so all these components can correctly anticipate when the transmitter will be listening, when it will be sending power, and when which client(s) should be involved with the transmitter's current function.

There are many issues that can arise in isosynchronous network topologies. For example, timing resolution of fine events can be at the limits of many desired processors. Some of the isosynchronous topologies can require dedicated CPU usage during TPS, thereby making it difficult to use the processor for concurrent IoT and power and synchronization of the messaging can have higher than desired jitter. Moreover, some of these topologies require a dedicated radio even if client devices have a radio available. Moreover, the messaging protocol (e.g., the GO message) may be practical on other network typologies such as BLE or Wi-Fi which can force an extra radio to be added. Finally, broadcast messages are not reliable if nonsynchronotis timing is installed.

Rather than waiting for a message to pass up the stack a partial action can be taken at the lowest level to create a timing event that is then validated by higher levels. For example, at the lowest level the sequencer or M0 can actuate a GPIO pin when a preamble or end of message or other even during transmission is detected. This GPIO edge could fire an external or internal count down timer that is preloaded with an a priori value. The message is then passed up the stack for decoding. If the message is indeed for the device, is of the correct type and is the correct content, then the higher-level process could actuate a GPIO that the message is valid. The valid message GPIO can be combined (e.g., ANDed) with the counter to create an output that is tightly coupled with a fixed delay after the message was received.

A mirror process can be duplicated on the sending side. When a message is sent the sequencer or lowest level processor would actuate a GPIO to indicate when a message is started to be sent, finished or other event occurs, the same as on the receiver. That GPIO could also start a timer with the same fixed value as the receiver or at a predetermined offset as may be convent. When the sending timer expires then that output is low jitter tightly coupled with the receiving timer. On the sending side, the combining action (e.g., ANDing) can be neglected. Another advantage is that software can prospectively start an activity from the initial signal detection and then cancel it should the message prove to be one of non-interest.

This process can be implemented with similar on chip hardware or in a custom ASIC or FPGA. The counter could also be implemented in software. The decoupling of the signal reception events from decoding of the content of a message can greatly decrease jitter. While various embodiments have been described with respect to power delivery systems. Various embodiments of these techniques for reducing jitter can be used within any system with communications. In addition, these techniques may be applied for syncing other actions such as microphones, light shows, and the like that can use an out of (communication) band pulsed energy source as a part of a synchronization process.

FIG. 7 is a flowchart illustrating an example of a set of operations 700 for adjusting cycle faming in accordance with some embodiments. As illustrated in FIG. 7, during scheduling operation 702 a charger (or other communication node) sends out a schedule to a new client over a communication network via an asynchronous communications channel. During messaging operation 704, the charger (or other communication node) can send a second message to the new client to tone now. The new client waits to tone until the time specified in the schedule during waiting operation 706. If determination operation 708, determines that the time has not been reached, determination operation 708 branches to waiting operation 706. If determination operation 708 determines that the time has been reached, then determination operation branches to timing operation 710 where the new client generates a tone.

The charger, during monitoring operation 712, detects the tone generated by the new client and then computes, during timing operation 714, a time delta based on the time the one was detected at the charger compared to the charger sent schedule. After computing the time delta, the charger sends the time delta to the new client using sending operation 716. Upon receipt of the time delta, the new client uses adjustment operation 718 to adjust the TPS cycle framing.

FIG. 8 depicts a sequence diagram illustrating communications between components to create an event synchronization in accordance with some embodiments. As illustrated in FIG. 8, a proxy (e.g., a data radio or communication radio) can send a discover message to a new client. The client can respond with a join message. The proxy can then send a time tone request to the client which is passed to a complex logic block (e.g., a complex programmable logic device or ASIC). The complex logic block resets a counter and submits the time tone request to a receiver which transmits the tone to a transmitter. Using the time of the received tone, a time delta can be computed which is then sent to the client using the proxy. The client adjusts the counters so that the framing cycle of the client is aligned (e.g., corrected for delay). Upon completion of the timing correction an acknowledgment can be sent to the proxy and then to the transmitter. The TPS cycle resumes or starts a traditional power cycle which is shown in the remaining part of FIG. 8.

FIG. 9 depicts a timing diagram illustrating example data communications between components of a system in accordance with some embodiments. These communications can be used to coordinate events and reduce the amount of jitter within the system. Moreover, the time scale shown in FIG. 9 is arbitrary and is not necessarily monotonic. As such, the communication shown in FIG. 9 are only intended to show one potential sequence that may be used.

“Start” (1) is the time from an input to the transmitting radio processor that may include both software and hardware delays that may be fixed or variable. “RF_Transmit” (2) is the period during which the transmitting radio is sending a synchronization message. “RF_Receive” (2) shows the transmitted message arriving at the receiver. The “TX_Hack” (3) and “RX_Hack” (3) show an event during radio transmit and receive creating a signal event. This signal event could be any event such as completion of preamble or as in this case the end of signal. An example of an event could be one that can be detected with little jitter. The Hack signals start a timer in both the transmitter and receiver. The timer value can be the same if the skew between the transmitter and receiver hack signals is expected to be identical or the timer initialization value may be different to correct any skew between the hack signals. Further the timer values can be statically and/or dynamically set and/or calibrated by measuring one-way and/or round trip timing.

Once the timer on the transmitter expires (5) the rising edge of the TX_Timer (5) acts as a synchronization signal to the transmitter system. In the receiver, the software stacks (and/or hardware if so implemented) decode the content of the message. RX_Valid (4) can be used to validate that the message is a sync signal and if so validated the sacks generate a signal to indicate a valid message in “RX_Valid.” The RX_Timer signal can be ANDed with RX_Valid to create a “RX_Sync” signal. A rising edge on RX_Sync (5) can be used as a synchronization signal to the receiver system. The logic can be implemented with inverted logic and different combination of gates to recover a synchronization signal. The start of the next cycle (6) begins at timing interval 6.

Additionally, in some embodiments the signal, which is primarily referred to herein as a RF waveform, can alternatively or additionally take the form of any signal such as baseband or photonic. In some embodiments, the signal, which is primarily referred to herein as an asynchronous signal may also take the form as a synchronous signal. Further, the logic, sequencing and timing described is exemplary and can be implemented in many alternative forms such as with inverted logic and different combination of gates to recover synchronization. A network is defined as any configuration of devices and or subsystems with two or more nodes that can communicate using any form.

FIG. 10 depicts a flow chart illustrating a set of operations 1000 for adding a new client in accordance with some embodiments. As illustrated in FIG. 10, sending operation 1002 sends a new time to a transmitter and receiver after a host decides to add a new client. During pause operation 1004, a pause notification can be sent to current clients to temporarily pause. The pause notification may indicate a number of cycles that the current clients should pause. In some embodiments, a resume signal may be used to resume the normal client activity. A communication message can then be sent to the new receiver client to tone during signaling operation 1006. The client can process the communication message and starts the TPS cycle and tone during processing operation 1008.

The receiver can generate a time tag and hand the tag to the host during tagging operation 1010. In some cases, the toning may be repeated a specified number of times (e.g., one additional time, five additional times, etc.) Determination operation 1012 can determine if this process needs to be repeated. If the determination operation 1012 determines that the number of repeats has not been reached, then determination operation 1012 branches to tagging operation 1010. If the determination operation 1012 determines that the number of repeats has been reached, then determination operation 1012 branches to calculation operation 1014 where the host calculates the time error using the time tags, the expected toning time, known delays, and/or other information.

During notification operation 1014, the host transmitter can notify the new client receiver to adjust the TPS cycle framing by the timing error. The new client adjusts the TPS cycle framing during adjustment operation 1016 and in some embodiments, the host can inform all the clients to resume.

In some embodiments, the implementations can be based on just the timing of the power signal. If the client measures a power pulse arrives relative to when it was expected the power pulse to arrive, the power client can adjust the client's timing schedule with an offset to match the host's timing schedule. Regardless of which component adjusts the timing schedule, along as one party (either host or client) senses the time deltas of when a pulse is expected and when the pulse arrives, and then one party adjusts timing to resolve the difference then ISO synchronous network traffic can be avoided.

FIG. 11 depicts a block diagram illustrating example components of a representative mobile device or tablet computer 1100 with a wireless power receiver or client in the form of a mobile (or smart) phone or tablet computer device, according to an embodiment. Various interfaces and modules are shown with reference to FIG. 11, however, the mobile device or tablet computer does not require all of the modules or functions for performing the functionality described herein. It is appreciated that, in many embodiments, various components are not included and/or necessary for operation of the category controller. For example, components such as Global Positioning System (GPS) radios, cellular radios, and accelerometers may not be included in the controllers to reduce costs and/or complexity. Additionally, components such as ZigBee™ radios and RFID transceivers, along with antennas, can populate the Printed Circuit Board.

The wireless power receiver client can be a power receiver client 103 of FIG. 1, although alternative configurations are possible. Additionally, the wireless power receiver client can include one or more RF antennas for reception of power and/or data signals from a power transmission system, e.g., wireless power transmission system 101 of FIG. 1.

FIG. 12 depicts a diagrammatic representation of a machine, in the example form, of a computer system within which a set of instructions, for causing the machine to perform any one or more of the methodologies discussed herein, may be executed.

In the example of FIG. 12, the computer system includes a processor, memory, non-volatile memory, and an interface device. Various common components (e.g., cache memory) are omitted for illustrative simplicity. The computer system 1200 is intended to illustrate a hardware device on which any of the components depicted in the example of FIG. 1 (and any other components described in this specification) can be implemented. For example, the computer system can be any radiating object or antenna array system. The computer system can be of any applicable known or convenient type. The components of the computer system can be coupled together via a bus or through some other known or convenient device.

The processor may be, for example, a conventional microprocessor such as an Intel Pentium microprocessor or Motorola power PC microprocessor. One of skill in the relevant art will recognize that the terms “machine-readable (storage) medium” or “computer-readable (storage) medium” include any type of device that is accessible by the processor.

The memory is coupled to the processor by, for example, a bus. The memory can include, by way of example but not limitation, random access memory (RAM), such as dynamic RAM (DRAM) and static RAM (SRAM). The memory can be local, remote, or distributed.

The bus also couples the processor to the non-volatile memory and drive unit. The non-volatile memory is often a magnetic floppy or hard disk, a magnetic-optical disk, an optical disk, a read-only memory (ROM), such as a CD-ROM, EPROM, or EEPROM, a magnetic or optical card, or another form of storage for large amounts of data. Some of this data is often written, by a direct memory access process, into memory during execution of software in the computer 1200. The non-volatile storage can be local, remote, or distributed. The non-volatile memory is optional because systems can be created with all applicable data available in memory. A typical computer system will usually include at least a processor, memory, and a device (e.g., a bus) coupling the memory to the processor.

Software is typically stored in the non-volatile memory and/or the drive unit. Indeed, for large programs, it may not even be possible to store the entire program in the memory. Nevertheless, it should be understood that for software to run, if necessary, it is moved to a computer readable location appropriate for processing, and for illustrative purposes, that location is referred to as the memory in this paper. Even when software is moved to the memory for execution, the processor will typically make use of hardware registers to store values associated with the software, and local cache that, ideally, serves to speed up execution. As used herein, a software program is assumed to be stored at any known or convenient location (from non-volatile storage to hardware registers) when the software program is referred to as “implemented in a computer-readable medium”. A processor is considered to be “configured to execute a program” when at least one value associated with the program is stored in a register readable by the processor.

The bus also couples the processor to the network interface device. The interface can include one or more of a modem or network interface. It will be appreciated that a modem or network interface can be considered to be part of the computer system. The interface can include an analog modem, ISDN modem, cable modem, token ring interface, satellite transmission interface (e.g. “direct PC”), or other interfaces for coupling a computer system to other computer systems. The interface can include one or more input and/or output devices. The I/O devices can include, by way of example but not limitation, a keyboard, a mouse or other pointing device, disk drives, printers, a scanner, and other input and/or output devices, including a display device. The display device can include, by way of example but not limitation, a cathode ray tube (CRT), liquid crystal display (LCD), or some other applicable known or convenient display device. For simplicity, it is assumed that controllers of any devices not depicted in the example of FIG. 12 reside in the interface.

In operation, the computer system 1200 can be controlled by operating system software that includes a file management system, such as a disk operating system. One example of operating system software with associated file management system software is the family of operating systems known as Windows® from Microsoft Corporation of Redmond, Wash., and their associated file management systems. Another example of operating system software with its associated file management system software is the Linux operating system and its associated file management system. The file management system is typically stored in the non-volatile memory and/or drive unit and causes the processor to execute the various acts required by the operating system to input and output data and to store data in the memory, including storing files on the non-volatile memory and/or drive unit.

Some portions of the detailed description may be presented in terms of algorithms and symbolic representations of operations on data bits within a computer memory. These algorithmic descriptions and representations are the means used by those skilled in the data processing arts to most effectively convey the substance of their work to others skilled in the art. An algorithm is here, and generally, conceived to be a self-consistent sequence of operations leading to a desired result. The operations are those requiring physical manipulations of physical quantities. Usually, though not necessarily, these quantities take the form of electrical or magnetic signals capable of being stored, transferred, combined, compared, and otherwise manipulated. It has proven convenient at times, principally for reasons of common usage, to refer to these signals as bits, values, elements, symbols, characters, terms, numbers, or the like.

It should be borne in mind, however, that all of these and similar terms are to be associated with the appropriate physical quantities and are merely convenient labels applied to these quantities. Unless specifically stated otherwise, as apparent from the following discussion, it is appreciated that throughout the description, discussions utilizing terms such as “processing” or “computing” or “calculating” or “determining” or “displaying” or the like, refer to the action and processes of a computer system, or similar electronic computing device, that manipulates and transforms data represented as physical (electronic) quantities within the computer system's registers and memories into other data similarly represented as physical quantities within the computer system memories or registers or other such information storage, transmission or display devices.

The algorithms and displays presented herein are not inherently related to any particular computer or other apparatus. Various general purpose systems may be used with programs in accordance with the teachings herein, or it may prove convenient to construct more specialized apparatus to perform the methods of some embodiments. The required structure for a variety of these systems will appear from the description below. In addition, the techniques are not described with reference to any particular programming language, and various embodiments may thus be implemented using a variety of programming languages.

In alternative embodiments, the machine operates as a standalone device or may be connected (e.g., networked) to other machines. In a networked deployment, the machine may operate in the capacity of a server or a client machine in a client-server network environment or as a peer machine in a peer-to-peer (or distributed) network environment.

The machine may be a server computer, a client computer, a personal computer (PC), a tablet PC, a laptop computer, a set-top box (STB), a personal digital assistant (PDA), a cellular telephone, an iPhone, a Blackberry, a processor, a telephone, a web appliance, a network router, switch or bridge, or any machine capable of executing a set of instructions (sequential or otherwise) that specify actions to be taken by that machine.

While the machine-readable medium or machine-readable storage medium is shown in an exemplary embodiment to be a single medium, the term “machine-readable medium” and “machine-readable storage medium” should be taken to include a single medium or multiple media (e.g., a centralized or distributed database, and/or associated caches and servers) that store the one or more sets of instructions. The term “machine-readable medium” and “machine-readable storage medium” shall also be taken to include any medium that is capable of storing, encoding or carrying a set of instructions for execution by the machine and that cause the machine to perform any one or more of the methodologies of the presently disclosed technique and innovation.

In general, the routines executed to implement the embodiments of the disclosure, may be implemented as part of an operating system or a specific application, component, program, object, module or sequence of instructions referred to as “computer programs.” The computer programs typically comprise one or more instructions set at various times in various memory and storage devices in a computer, and that, when read and executed by one or more processing units or processors in a computer, cause the computer to perform operations to execute elements involving the various aspects of the disclosure.

Moreover, while embodiments have been described in the context of fully functioning computers and computer systems, those skilled in the art will appreciate that the various embodiments are capable of being distributed as a program product in a variety of forms, and that the disclosure applies equally regardless of the particular type of machine or computer-readable media used to actually effect the distribution.

Further examples of machine-readable storage media, machine-readable media, or computer-readable (storage) media include but are not limited to recordable type media such as volatile and non-volatile memory devices, floppy and other removable disks, hard disk drives, optical disks (e.g., Compact Disk Read-Only Memory (CD ROMS), Digital Versatile Disks, (DVDs), etc.), among others, and transmission type media such as digital and analog communication links.

Unless the context clearly requires otherwise, throughout the description and the claims, the words “comprise,” “comprising,” and the like are to be construed in an inclusive sense, as opposed to an exclusive or exhaustive sense; that is to say, in the sense of “including, but not limited to.” As used herein, the terms “connected,” “coupled,” or any variant thereof, means any connection or coupling, either direct or indirect, between two or more elements; the coupling of connection between the elements can be physical, logical, or a combination thereof. Additionally, the words “herein,” “above,” “below,” and words of similar import, when used in this application, shall refer to this application as a whole and not to any particular portions of this application. Where the context permits, words in the above Detailed Description using the singular or plural number may also include the plural or singular number respectively. The word “or,” in reference to a list of two or more items, covers all of the following interpretations of the word: any of the items in the list, all of the items in the list, and any combination of the items in the list.

The above detailed description of embodiments of the disclosure is not intended to be exhaustive or to limit the teachings to the precise form disclosed above. While specific embodiments of, and examples for, the disclosure are described above for illustrative purposes, various equivalent modifications are possible within the scope of the disclosure, as those skilled in the relevant art will recognize. For example, while processes or blocks are presented in a given order, alternative embodiments may perform routines having steps, or employ systems having blocks, in a different order, and some processes or blocks may be deleted, moved, added, subdivided, combined, and/or modified to provide alternative or subcombinations. Each of these processes or blocks may be implemented in a variety of different ways. Also, while processes or blocks are, at times, shown as being performed in a series, these processes or blocks may instead be performed in parallel, or may be performed at different times. Further, any specific numbers noted herein are only examples: alternative implementations may employ differing values or ranges.

The teachings of the disclosure provided herein can be applied to other systems, not necessarily the system described above. The elements and acts of the various embodiments described above can be combined to provide further embodiments.

Any patents and applications and other references noted above, including any that may be listed in accompanying filing papers, are incorporated herein by reference. Aspects of the disclosure can be modified, if necessary, to employ the systems, functions, and concepts of the various references described above to provide yet further embodiments of the disclosure.

These and other changes can be made to the disclosure in light of the above Detailed Description. While the above description describes certain embodiments of the disclosure, and describes the best mode contemplated, no matter how detailed the above appears in text, the teachings can be practiced in many ways. Details of the system may vary considerably in its implementation details, while still being encompassed by the subject matter disclosed herein. As noted above, particular terminology used when describing certain features or aspects of the disclosure should not be taken to imply that the terminology is being redefined herein to be restricted to any specific characteristics, features, or aspects of the disclosure with which that terminology is associated. In general, the terms used in the following claims should not be construed to limit the disclosure to the specific embodiments disclosed in the specification, unless the above Detailed Description section explicitly defines such terms. Accordingly, the actual scope of the disclosure encompasses not only the disclosed embodiments, but also all equivalent ways of practicing or implementing the disclosure under the claims.

While certain aspects of the disclosure are presented below in certain claim forms, the inventors contemplate the various aspects of the disclosure in any number of claim forms. For example, while only one aspect of the disclosure is recited as a means-plus-function claim under 35 U.S.C. § 112, ¶6, other aspects may likewise be embodied as a means-plus-function claim, or in other forms, such as being embodied in a computer-readable medium. (Any claims intended to be treated under 35 U.S.C. § 112, ¶6 will begin with the words “means for”.) Accordingly, the applicant reserves the right to add additional claims after filing the application to pursue such additional claim forms for other aspects of the disclosure.

The detailed description provided herein may be applied to other systems, not necessarily only the system described above. The elements and acts of the various examples described above can be combined to provide further implementations of the invention. Some alternative implementations of the invention may include not only additional elements to those implementations noted above, but also may include fewer elements. These and other changes can be made to the invention in light of the above Detailed Description. While the above description defines certain examples of the invention, and describes the best mode contemplated, no matter how detailed the above appears in text, the invention can be practiced in many ways. Details of the system may vary considerably in its specific implementation, while still being encompassed by the invention disclosed herein. As noted above, particular terminology used when describing certain features or aspects of the invention should not be taken to imply that the terminology is being redefined herein to be restricted to any specific characteristics, features, or aspects of the invention with which that terminology is associated. In general, the terms used in the following claims should not be construed to limit the invention to the specific examples disclosed in the specification, unless the above Detailed Description section explicitly defines such terms. Accordingly, the actual scope of the invention encompasses not only the disclosed examples, but also all equivalent ways of practicing or implementing the invention. 

What is claimed is:
 1. A method for adding a new client to a communication system, the method comprising: generating, at a host device, a beacon schedule; transmitting, from the host device to the new client, a communication message instructing the new client to generate a beacon according to the beacon schedule; calculating, at the host, a timing error based on the time the beacon was detected and the beacon signals; and communicating the timing error to the new client, wherein upon receiving the timing error, the new client adjust cycle framing by the timing error.
 2. The method of claim 1, wherein the communication system includes a wireless power transmission and reception processing system and wherein the beacons include tones used to synchronize charging cycles.
 3. The method of claim 1, wherein the communication message includes instructions for the new client to generate multiple beacons and the method further comprises averaging multiple timing errors based on the times the beacons were detected.
 4. The method of claim 1, wherein the communication message includes instructions for the new client to generate multiple beacons and the method further comprises removing any time timing errors that are above a threshold.
 5. The method of claim 1, wherein calculating the timing error includes using estimates of known timing delays within the communication system.
 6. The method of claim 1, further comprising: sending, from the host device, a temporary suspension message to existing clients of the communication system, wherein the temporary suspension message causes the existing clients to suspend beaconing.
 7. A wireless power transmission system comprising: an adaptively-phased antenna array having multiple radio frequency (RF) antennas; control circuitry operatively coupled to the multiple RF antennas, the control circuitry configured to: identify a device to synchronize timing within the wireless power transmission system; and transmit a communication message instructing the device to generate a beacon according to a beacon schedule; calculate a timing error based, at least in part, on the time the beacon was detected; and instruct the new client to adjust cycle framing by the timing error.
 8. The wireless power transmission system of claim 7, wherein the control circuitry sends a message to one or more devices to temporarily cease communications.
 9. The wireless power transmission system of claim 7, wherein the device is a new device and the message to the one or more devices is a broadcast message instructing the one or more devices to cease communications for a specific number of timing cycles.
 10. The wireless power transmission system of claim 7, wherein the device is a new device detected by the control circuitry.
 11. The wireless power transmission system of claim 7, wherein the device is an existing device that the control circuitry determined was communicating with timing delays above a desired threshold.
 12. The wireless power transmission system of claim 7, wherein the control circuitry calculates the timing error based, at least in part, on estimates of known timing delays within the wireless power transmission system.
 13. The wireless power transmission system of claim 7, wherein the beacons include tones used to synchronize charging cycles.
 14. The wireless power transmission system of claim 13, wherein the control circuitry is further configured to add the device to a power delivery schedule.
 15. A method of operating a tone power scheduler for calibrating communication timing, the method comprising: establishing communications with a wireless power transmission system in a multipath wireless power delivery environment, monitoring the communications for one or more tones from a communication node according to a schedule provided by the tone power scheduler; and directing one or more antennas associated with the tone power scheduler to transmit a timing error to the communication node allowing the communication node to adjust a framing cycle to improve the communication time between the communication node and other components of the wireless power transmission system.
 16. The method of claim 15, wherein the communications include additional information about the communication node, the additional information comprising a device type or device charging information.
 17. The method of claim 15, wherein the communication message includes instructions for the communication node to generate multiple beacons and the method further comprising: computing multiple timing errors by computing a timing error based on each of the multiple beacons; and averaging multiple timing errors based on the times the beacons were detected.
 18. The method of claim 15, wherein the communication message includes instructions for the communication node to generate multiple beacons and the method further comprises removing any time timing errors that are statistical outliers.
 19. The method of claim 15, wherein calculating the timing error includes using estimates of known timing delays within the wireless power transmission system.
 20. The method of claim 15, wherein communications instructing the communication node to tone are sent asynchronously. 